Skip to content

WAL frame checksum mismatch #1622

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sivukhin opened this issue May 30, 2025 · 1 comment · May be fixed by #1647
Open

WAL frame checksum mismatch #1622

sivukhin opened this issue May 30, 2025 · 1 comment · May be fixed by #1647
Milestone

Comments

@sivukhin
Copy link
Contributor

Limbo crashes for me locally if shell will be restarted WAL is big enough:

$> limbo --version
limbo 0.0.21

$> limbo a.db
limbo> CREATE TABLE t(x);
limbo> INSERT INTO t VALUES (randomblob(512 * 1024)); 
limbo> INSERT INTO t SELECT * FROM t;
limbo> INSERT INTO t SELECT * FROM t;
limbo> INSERT INTO t SELECT * FROM t;
limbo> INSERT INTO t SELECT * FROM t;
limbo> ^C
Interrupted. Exiting...

$> limbo a.db
thread 'main' panicked at core/storage/sqlite3_ondisk.rs:1495:17:
WAL frame checksum mismatch. Expected (3480643840, 2904012637), Got (4135411069, 2138363541)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[1]    64670 IOT instruction (core dumped)  limbo a.db
@jussisaurio jussisaurio added this to the 0.1.0 milestone May 30, 2025
@el-yawd
Copy link
Contributor

el-yawd commented Jun 2, 2025

I'm working on this, I've already "solved", but wanna be sure it's correct and not biased to this specific case

@el-yawd el-yawd linked a pull request Jun 3, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants